- UK Justice System Failing Cybercrime Victims, Cyber Helpline Finds
- Best Black Friday deals 2024: 170+ sales live now featuring some of the lowest prices ever
- 기고 | 빠르게 변화하는 시대에 대응하는 IT리더의 특징 4가지
- Francisco Gonzalo, CIO de Sacyr: “Hemos identificado más de 70 casos de uso de IA generativa"
- 칼럼 | 클라우드 컴퓨팅 현실, 10년 전보다 나쁘다?
Predictable AWS cloud deployment resources allow full account takeover
S3 bucket name-squatting
CDK is AWS’ open-source framework organizations use to define their infrastructure as code (IaC), the process of provisioning and managing computing resources by using code rather than configuring physical hardware manually, using programming languages like Python, TypeScript, or JavaScript.
In order to be able to use the AWS CDK, users need to bootstrap their environment to prepare it for CDK stack deployments. CDK bootstrapping creates a CloudFormation template file that deploys the essential infrastructure components, including access roles, configurations, policies, and an S3 staging bucket.
The created staging S3 bucket follows a specific naming pattern: cdk-{qualifier}-assets-(account-ID}-{Region}. The issue stems from the fact that users running the CDK bootstrap command rarely customize the “qualifier,” which is defaulted by AWS to “hnb659fds.”